*************************************************** ** NP00646 FILE ** ** DATE = 10/08/97 ** PHONE = 8-444-0017 ** CONTACT = SANDY PETERSON ** C/T = RD0011 ** USER = SANDYPE NODE = RALVM29 ** *************************************************** APARTXT NA02880 = appn gets in a loop in xid exchange with a len node, missing control vector with the cp name. However, config does have the cp name in it. Problem is the config objects indicate cp to cp sessions on this link, although the config tool screen shows cp to cp session button greyed out. Appn dump does not show any trace of the link station control block for the len node. It was discarded with no error indication. APARTXT NA02915 = appn abends with pexit code f023 in xxxims00 when using the appn view -node, -dir, -isr commands. APARTXT NA03025 = Scram prematurely accessed the kernel ifnet/ifaddr structures during ipl causing some of the adapter/routing tables not built. APARTXT NA03049 = DHCP/BOOTP relay agent uses YIADDR instead of GI field in bootp frame to get ip addr for routing APARTXT NA03069 = The display of the interface utilization (operations/network sta tistics/interface utilization monitor is not displaying entries for some Frame Relay interfaces. APARTXT NA03092 = Mss and the 6611 connnected via 6611 TR --8272--155mb fiber to the Mss will not allow OSPF to come Full. Acee found that the max packet size for 6611 ospf/gated was 4k and the Mss was send ing us 4490. See Acee for futher details. APARTXT NA03100 = Bootp protocol requires that the server accept request with either 0.0.0.0 source addresses or non-0 source addresses. However, some servers reject request that contain 0.0.0.0 as source when the frames are unicast. When the 6611 forwards a bootp request it does not change the 0.0.0.0 source address (and this conforms to the RFC) and converts the frame to a unicast. Some non-conforming servers discard such requests. This APAR request 6611 to perform like 2210 and Cisco routers that go ahead and change the source address to their own. APARTXT NA03106 = Router got rebooted immediately - the schedule time for a config. change does not work if the router was upgraded by a migration procedure. APARTXT NA03211 = required for build APARTXT NA03214 = When a 6611 is configured for transparent bridging and NETBIOS over DLSw without configuring SNA over DLSw, NETBIOS does not work. The workaround is to turn on SNA over DLSw at the box level. APARTXT NA03213 = New design only impact SCRAM and some SNMP code. APARTXT NA03115 = Internal IP address not always showing up on adapter cards. APARTXT NA03212 = When adding reject/discard static route it will show up as a noinstall route unless it is also designated an interface route. APARTXT NA03126 = DLS SAPs in bridge code remain closed after config change which restarts DLS. APARTXT NA03134 = A gated error log entry is being made for a condition which is normal and timing dependent. APARTXT NA03215 = APPN does not come up on router due to lack of storage to pcreate new process APARTXT NA03216 = ipForwardMetric1 and ipForwardMetric2 should be -1 for routes with 0 metric (e.g., static routes). APARTXT NA03155 = Scram abending with dump. APARTXT NA03217 = Today GateD tries to reverse the effects of redirects. This is prone to error and it would be better to disable all together when a routing protocol is being run. APARTXT NA03218 = With the IPL speedup, GateD can be started before snmpd is ready receive connections from smux agents. This results in the following log entry: <28>Jul 25 05:56:41 gated[7078]: snmp_connect: CONNECT: smux_init: systemError [join_tcp_server failed: Connection refused] (Connection refused) This message will no longer be logged initially since GateD will re-attempt to connect 60 seconds later. If unsuccessful than an error will be logged. APARTXT NA03173 = When 6611 was upgraded from v1r3 to v1r4 (PTF644), decnet does not learn any routes across the wan (frame-relay) network. It does learn all the routes from local attached lan segment tho IP and IPX work fine across frame relay. Customer does not define DLCI number, router learns the DLCI from frame-relay switch. APARTXT NA03179 = Recompilation of bos modules to preserve data integrity. APARTXT NA03225 = ibmipFilterPermitDeny never was returned correctly. APARTXT NA03187 = When customer has transparent subnetting turned on and places a host configured to an IP address different from the subnet of the TR port, upon pinging, the port hangs. The 6611 140 has to be rebooted and there is suspicion that card damage results -- as the card has had to be replaced in some cases. APARTXT NA03219 = psna extract to pick up current psna level APARTXT NA03220 = When you load a machine with a hard disk whose capacity is > 2.1G, and try to load it from a CE tape, the reload fails with an error message that there is not enough staroage on the disk. APARTXT NA03222 = Cannot create gateway reject or blackhole route. Actually, this should be an interface route anyway if 127.0.0.1 is specified but we don't want to force the customer to configure this (the Config Tool cannot be changed at this point). APARTXT NA03223 = Internal Enhancements for NP00646 APARTXT NA03224 = Slow memory leak when previous instances of LSA are on retransmission queues in routing domain when new instance of LSA is introduced. Fast memory leak when 2 routers are erronenously given the same router ID. APARTXT NA03256 = appn abends with F00A0000. ENDSET COMPID FOR PTF NP00646 = 564801600,140 PRODID FOR PTF NP00646 = 5648016,Multiprotocol Network Program PREREQ FOR NP00646 = NONE ENDSET COREQ FOR NP00646 = NONE ENDSET SUP FOR NP00646 = NONE ENDSET IFREQ FOR NP00646 = NONE ENDSET MEMO TO USERS = +---------------------------------------------------------------+ | | | MEMO FOR NP00646 | | | +---------------------------------------------------------------+ CONTENTS OF THIS MEMO _____________________ o Description of Supersede and Prerequisite PTFs o Installation instructions for NP00646 o Engineering PTFs with contents included in Production PTFs SUPERSEDE AND PREREQUISITE PTFS ________________________________ NP00646 is a supersede PTF. There are no prerequisite PTFs for NP00646. Any user at base V1R4 can apply this ptf. Having PTFs NP00620, NP00623, NP00625, NP00627, NP00629, NP00640, NP00642, NP 00644, NP00645 though not required, will not prevent NP00646 from being appli ed. All the fixes contained in NP00645,NP00644, NP00642, NP00640, NP00629, NP00627, NP00625, NP00623 and NP00620 are contained in NP00646. Users at any release levels other than V1R4 must migrate to that level (using NP99933, NP99932 or NP99931) and be committed at that lev el before applying NP00646. Note: NP99933 is an MES Upgrade to V1R4 at PTF level NP00644. NP99932 is an MES Upgrade to V1R4 at PTF level NP00625. NP99931 is an MES Upgrade to V1R4 base. PTF INSTALL INSTRUCTIONS FOR NP00646 ____________________________________ Potential problems or delays in the installation procedure can be avoided if you perform certain actions first. CLEANING UP THE 6611 TRANSFER DIRECTORY Receiving installation files places them in the transfer directory of the 6611. If you know you have unnecessary files in the transfer directory (such as outdated dumps or reports), delete the files before beginning the installation. Refer to "Delete Transfer Directory Files" in the Operations chapter of the IBM Multiprotocol Network Program Operations and Problem Management manual for details. STOPPING TRACES Before beginning the installation process for any update, stop all trace activities. Active traces might cause installation to fail because of insufficient space. Refer to the Problem Determination chapter of the IBM Multiprotocol Network Program Operations and Problem Management manual for information on stopping traces. In particular, it is important that IP routing (gated) protocol traces should be stopped before installing this PTF. HANDLING DEVELOPMENT PTFS Before beginning the installation process for any software update, check to see if you have any development PTFs on your system. Development PTFs may be identified as containing the characters FX in their names, for example: Name: mpnp.obj NP00001 ---------------------- Fix ID Release ---------------------- FX00001 01.01.0000.0001 If you know that you have development PTFs on your system, call your IBM Support Center and provide the following information: o The development PTFs that are already on your system o The software updates you wish to install INSTALLING SOFTWARE UPDATES Software updates are installed from the transfer directory using the Software Installation and Maintenance Facility of the Multiprotocol Network Program V1R3 Supplement(SD35-0238). This is a multiphase process that permits the software updates to be tested before making them a permanent part of the Multiprotocol Network Program. When updating software, the first step after importing the software update is to apply the software update. After a software update is applied to a 6611, it can be activated at a later time. You can specify the maintenance level and the date and time of the activation. The 6611 will be re-IPLed at activation time. Thus, the application of a PTF is not directly coupled with the re-IPL of the router. Any software update that is applied, but not activated in the currently running 6611, can be rejected at any time. A software update must be active before it can be committed. Warning: When you commit the software update, the change is permanent. There are several rules to consider when installing software updates that have dependencies: o Software updates cannot be applied until their prerequisite software updates have been applied. o Applied software updates cannot be committed until their prerequisite software updates have been committed. Possible Messages When Applying PTFs: If there is not sufficient space available, you will see a system message similar to: Installation failed. Please press enter to view the detailed information. (Assuming Enter is pressed, this detailed message is displayed:) installp could not complete because there is not enough space in file system /usr. It needs 476 more 1K blocks. The space available in /usr is less than the minimum required for this operation. The selected install operation will not be started now. Press Enter to continue. If there are more than 1000 1K blocks free in each file system, then you will see different messages depending on whether there was sufficient room for the PTFs you selected to apply. NOTE: If you have insufficient space in the file systems other than /tmp and you have commited all prior PTF's, you must contact IBM service. IBM service will make the appropriate adjustments to the file systems. If you select multiple PTFs to be applied and there is room for some, but not all, only the ones that fit will be applied. The log file pd_update.log in the transfer directory will inform you of this. To perform software updates from the System Manager: 1. Log in to the System Manager using a controlling user ID. 2. Select Software Installation and Maintenance on the System Manager main menu. Follow this procedure to install your software update using the System Manager: Step 1 Your software update is sent to you on diskettes or tape. The software update must be moved to the transfer directory for installation. Before proceeding, refer to "Recommended Software Pre-Installation Actions" for suggested actions if you have not already done so. Step 2 Select Receive Software Updates from the Software Installation and Maintenance menu to move the update files to the transfer directory in the 6611. These import methods are available: * FTP * Modem * Tape * Diskette Before receiving any software files, the system validates that enough space is available in the transfer directory. NOTE: Steps 3 and 4 are optional steps for informational purposes only and are not required for this installation Step 3 Select List Software Updates in the Transfer Directory to view a list of the software in the transfer directory of the 6611, Step 4 Select List All Problems Fixed by Software Updates to list the problems fixed by the software updates in the transfer directory. Step 5 Select Apply Software Updates to install the software updates on the 6611. The installation ends without a re-ipl, and you are returned to the Software Installation Maintenance menu. Step 6 Select Activate Applied Software Updates to activate the applied software updates. In the first selection screen, select NP00646. In the second selector screen you must use "none" as a selection if that is the only choice or if you wish to select no EPTF's. COMMITTING THE SOFTWARE UPDATE (PTF NP00646) CAUTION: When you commit the software update, the change is permanent. You will not be able to reverse the commit. When PTF NP00646 is committed, underlying PTFs are committed also. All EPTFs(FX....) are rejected when NP00646 is committed. Step 1 Select Commit Active Software Updates to commit the activated software updates. Refer to Chapter 5 "Software Installation and Maintenance" in the Multiprotocol Network Program Supplement Version 1 Release 3 (SD35-0238) more installation information. ------------------------------------------------------------ Installation of PTF NP00646 along with the prerequisite and corequisite PTF's, will alleviate the need for the engineering PTF's listed below to reside on your machine. NOTE: If you are currently running with an Engineering PTF that is not on the list below, contact your IBM Service representative for possible additional instructions. FX62001 FX62002 FX62301 FX62302 FX62303 FX62501 FX62502 FX64001 FX64201 FX64202 FX64203 FX64401 FX64402 FX64403 FX64501 FX64502 END OF MEMO - NP00646 ENDSET LABELTXT Selective Fix Package For use on MPNP V1, R4.0 only ENDSET ***************************************************